feat(deploy): migrate unified deploy to per-function API#384
Merged
yardend-wix merged 11 commits intofeature/functions-commandsfrom Mar 12, 2026
Merged
feat(deploy): migrate unified deploy to per-function API#384yardend-wix merged 11 commits intofeature/functions-commandsfrom
yardend-wix merged 11 commits intofeature/functions-commandsfrom
Conversation
Contributor
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/cli@0.0.44-pr.384.4b98c80Prefer not to change any import paths? Install using npm alias so your code still imports npm i "base44@npm:@base44-preview/cli@0.0.44-pr.384.4b98c80"Or add it to your {
"dependencies": {
"base44": "npm:@base44-preview/cli@0.0.44-pr.384.4b98c80"
}
}
Preview published to npm registry — try new features instantly! |
Add a new `functions list` CLI command that lists all deployed functions on the remote, showing automation counts. Restructure the functions command group to use an index.ts that registers subcommands. - Add ListFunctionsResponseSchema and FunctionInfo types to schema - Add listDeployedFunctions API client function - Create functions/list.ts command with automation count display - Refactor functions/deploy.ts export to getDeployCommand - Create functions/index.ts to register deploy + list subcommands - Update program.ts to use getFunctionsCommand - Add test mocks and 5 tests for the list command Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…support Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
yardend-wix
force-pushed
the
feature/functions-deploy-command
branch
from
ef46cce to
83f723c
Compare
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
yardend-wix
force-pushed
the
feature/unified-deploy-per-function
branch
from
67b9d55 to
3e8e89b
Compare
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Deleted Base44APIMock.ts (replaced by TestAPIServer.ts in main) and added mockFunctionsList / mockFunctionsListError methods to TestAPIServer so the functions-list tests work with the new test infrastructure. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
kfirstri
approved these changes
Mar 12, 2026
Combines per-function deploy additions (SingleFunctionDeployResponse, mockSingleFunctionDeploy) with delete/list/pull from the feature branch. Removes duplicate FunctionInfoSchema/ListFunctionsResponseSchema from auto-merge, keeping the AutomationSchema version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Base automatically changed from
feature/functions-deploy-command
to
feature/functions-commands
March 12, 2026 14:24
Resolve import conflict: use new formatDeployResult location from cli/commands/functions/. Fix deploy test assertion to match actual outro message. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Description
This PR integrates per-function deploy progress reporting into the unified
deploycommand. Instead of a single "Deploying your app..." spinner, the deploy flow now callsdeployFunctionsSequentiallywithonFunctionStartandonFunctionResultcallbacks, surfacing real-time[N/total]progress and per-function results to the user as each function deploys. ThedeployAllcore function is extended with an optionalDeployAllOptionsparameter to pass these callbacks through.Related Issue
None
Type of Change
Changes Made
core/project/deploy.ts: AddedDeployAllOptionsinterface withonFunctionStart/onFunctionResultcallbacks; replacedfunctionResource.pushwithdeployFunctionsSequentiallyand forwarded callbackscli/commands/project/deploy.ts: ReplacedrunTaskspinner with inline[N/total] Deploying <name>...progress log using the new callbacks; usesformatDeployResultto render each function's outcome inlinetests/cli/deploy.spec.ts: ReplacedmockFunctionsPushwithmockSingleFunctionDeployto align with the per-function API; removed stale "Deployment completed" assertions and dropped unnecessary function-push mocks from agent/connector-only test casesTesting
npm test)Checklist
docs/(AGENTS.md) if I made architectural changesAdditional Notes
The
runTaskwrapper (which showed a single spinner for the entire deploy) is removed in favour of granular per-function log steps, giving users visibility into which function is being deployed and its result at each stage.🤖 Generated by Claude | 2026-03-12 00:00 UTC